This repository has been archived by the owner on Jun 28, 2022. It is now read-only.
Use absolute path in build.gradle #1315
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM |
Codecov Report
@@ Coverage Diff @@
## master #1315 +/- ##
=========================================
Coverage 86.48% 86.48%
Complexity 3836 3836
=========================================
Files 378 378
Lines 15328 15328
Branches 1694 1694
=========================================
Hits 13256 13256
Misses 1622 1622
Partials 450 450Continue to review full report at Codecov.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relative paths do not work well in the new api-client-staging structure since it depends on the directory of execution. Switching to use absolute path with
projectDirsolves this problem.I will update the api-client-staging PR once the CI is fixed